Curse

Dex · Jan 24, 2006, 06:30 PM // 18:30

Quote:

Originally Posted by dimirpaw

*Waits as the ATI and Nivdia Flamers come*

lol It is a bit weird to support both heh, most people are loyal to only one.

Anyhow, I hope your problem gets fixed soon, good luck!

Brand loyalty is pointless. Just buy whatever product is best for you. I have about as many ATI products as nVidia products between my 4 computers...they both have their good and bad.

It's definitely not a compatibility issue between the video card and the game -- lots of people use that card with this game. It's also not a problem between the chipset and the game. NF4 is probably the most common chipset in use in AMD systems today. Heck, the system I'm using right now uses the NF4-SLi chipset. No problems. The only real nVidia problems that exist with GW are problems with certain cards/driver versions.

It's time to start troubleshooting. You're just going to have to start a process of elimination until you figure out what's causing the problem. It's not fun, I know, but if you build your own systems you'll have to do it eventually.

By the way, Imrik, I've built 3 different systems (granted, out of many) that had random lockups because of bad drive cables, but all of the bad cables were brand new, so don't rule that out just because your cables are new.

Have you looked in the System log in Windows to see if there's a critical error listed in the log when this happens? That could be a starting point for you. Also, and this might be a dumb question, but do you have all of the power cables connected properly? Make sure the power cables (including the one that goes directly to your video card) are properly seated.

imrik32 · Jan 24, 2006, 07:58 PM // 19:58

This is going to sound retarded but I'm not sure how to get to the system log.

An IDE cable 'may' be the problem, I'm using one from an older computer in there because I ONLY got 1 in my box, however that's connected to my cd drive.

Dex · Jan 24, 2006, 09:20 PM // 21:20

Here's a Microsoft article on using the Event Logs. Something like this would probably show up as an Error event in the System event log.

http://support.microsoft.com/default...308427&sd=tech

Like I said, a bad cable is not necessarily the most likely culprit, but it's one that baffles many people because they don't think to check it. Like I said, at this point you're probably going to have to start a process of elimination to find out what's wrong. You might start by taking everything out of your computer except what's absolutely necessary to run GW, see if it still crashes, and go from there.

imrik32 · Jan 24, 2006, 10:39 PM // 22:39

In my event log, DCOM and COM+ are giving me errors on the log roughly the time of my lockups, and this is what is says(I disabled both of them, COM+ just by clicking and DCOM with the DCOMbobulator tool program)

The COM+ Event System detected a bad return code during its internal processing. HRESULT was 800706BA from line 44 of d:\qxp_slp\com\com1x\src\events\tier1\eventsystemo bj.cpp. Please contact Microsoft Product Support Services to report this error.

and

DCOM got error "The service database is locked. " attempting to start the service netman with arguments "" in order to run the server:
{BA126AE5-2166-11D1-B1D0-00805FC1270E}

However, with it shut off I'm still getting COM+ errors

Dex · Jan 24, 2006, 11:39 PM // 23:39

Quote:

Originally Posted by imrik32

In my event log, DCOM and COM+ are giving me errors on the log roughly the time of my lockups, and this is what is says(I disabled both of them, COM+ just by clicking and DCOM with the DCOMbobulator tool program)

The COM+ Event System detected a bad return code during its internal processing. HRESULT was 800706BA from line 44 of d:\qxp_slp\com\com1x\src\events\tier1\eventsystemo bj.cpp. Please contact Microsoft Product Support Services to report this error.

and

DCOM got error "The service database is locked. " attempting to start the service netman with arguments "" in order to run the server:
{BA126AE5-2166-11D1-B1D0-00805FC1270E}

However, with it shut off I'm still getting COM+ errors

Hmm...you say you're using a Sound Blaster Audigy 2? Check this out:

http://forums.creative.com/creativelabs/board/message?board.id=soundblaster&message.id=428&view= by_date_ascending&page=4

Not sure if it's related, but it looks like this was causing lockups similar to what you're experiencing. I would try what the mod says on the 4th page of that thread and try downloading the newest drivers from the Creative Labs website.

imrik32 · Jan 24, 2006, 11:52 PM // 23:52

Well, I already thought of that, which is why atm my sound blaster isn't even in my pc anymore, I took it out to test it and I still lock up

Dex · Jan 25, 2006, 12:05 AM // 00:05

It looks like that problem isn't just caused by the driver. You might want to try removing all Creative software from your system. It also mentions updating some other Windows components like the MDAC.

Also:

Do you use Norton Antivirus or Security software?

Lagg · Jan 25, 2006, 12:43 AM // 00:43

I had that happen to me once after increasing my AGP Aperture size from 64mb to 256mb.

Have a look in your BIOS, and see what value it is at (probably 128mb or 256mb) and try lowering it to 64mb.

imrik32 · Jan 25, 2006, 01:32 AM // 01:32

Will that affect my graphics or anything? And when I go to remove the sound driver's it gives me an error

imrik32 · Jan 25, 2006, 02:47 AM // 02:47

I went into my BIOS to lower the aperture, and I went through every single thing and I cannot find a damn thing about aperture or like VGA or Video card stuff.

Yamat · Jan 25, 2006, 10:29 PM // 22:29

I've been playing GW on the same PC since the January Beta Weekend Events and this freezing only started happening in the last month or so...

I also have a NVidia card, and some friends of mine are having the same problem, and also have NVidia cards I think. A frustrating freeze happened to one of them while we were deep in SF last night, and I resolved to search the forums for info... low and behold!

I'm thinking it's a GW thing, not a NVidia thing. Sure, it may be due to having a NVidia card, but for many it seems the issue has been introduced recently...

Dex · Jan 25, 2006, 10:46 PM // 22:46

Quote:

Originally Posted by Yamat

I've been playing GW on the same PC since the January Beta Weekend Events and this freezing only started happening in the last month or so...

I also have a NVidia card, and some friends of mine are having the same problem, and also have NVidia cards I think. A frustrating freeze happened to one of them while we were deep in SF last night, and I resolved to search the forums for info... low and behold!

I'm thinking it's a GW thing, not a NVidia thing. Sure, it may be due to having a NVidia card, but for many it seems the issue has been introduced recently...

I don't think it's an nVidia issue. I use a GeForce 7800GT and two of my friends use 6800GT and 6800 Ultra and none of us are having problems.

Dex · Jan 26, 2006, 02:49 AM // 02:49

Any luck yet? I searched for those two error messages you posted, and most of what I come up with points at a software problem with an application that uses COM+. Two of the big ones I've come across are Norton and some of the Creative Labs companion apps, like Disc Detector, Control Center, and one of the processes that's tied to the Creative Mixer.

Did you try Google'ing those error messages?

Lagg · Jan 26, 2006, 02:52 PM // 14:52

Quote:

Originally Posted by imrik32

Will that affect my graphics or anything? And when I go to remove the sound driver's it gives me an error

No. AGP Aperture size is one of the big myths of graphic cards. Many people seem to think that a larger AGP aperture size means better performance, whereas it simply allocates (but doesn't reserve) system RAM to be used by the graphic card. If you have a graphic card with 128mb or more of on-board VRAM, you will never need more than a 64mb AGP aperture (if any at all, though entirely disabling the AGP aperture isn't recommended either).

Also, try using DriverCleaner to remove your sound drivers.

Quote:

Originally Posted by imrik32

I went into my BIOS to lower the aperture, and I went through every single thing and I cannot find a damn thing about aperture or like VGA or Video card stuff.

This is most unusual. Have you tried updating your BIOS? Unless this is a new computer, you may be running a rather obsolete mainboard. The AGP Aperture size is controlled by the chipset, so it should be in the chipset options of your BIOS.

Lagg · Jan 26, 2006, 03:02 PM // 15:02

Nevermind, you're running PCX (PCI-Express), the successor to AGP (so you obviously don't have AGP aperture size).

Can't help you there.

Try contacting Nvidia tech support and ask them if there is something like PCX aperture size.

Draikin · Jan 28, 2006, 01:28 PM // 13:28

The only lockups I ever experienced with Guild Wars were caused by a conflict with Antivir Personal Edition and by having "Cool & Quiet" enabled. It could still be a software problem, so make sure you shut down as many programs as possible that are running in the background before you start Guild Wars.

Gorebrex · Jan 28, 2006, 06:20 PM // 18:20

Im am also starting to have trouble too. Had 2 HEAVY in-game lags(couldnt move, or see new chat appear), had CTD when 1st attempted to login(lag was during 2nd login). Then, on 3rd, had PC restart spontaneously. Never had this happen in the month Ive been playing, nothing new in PC, its same as its been for before I got game. I also have a Nvidia card(FX5900, latest drivers. I have seen in-game that I am not alone in this lagginess...

And I always D/L updated drivers if I need them(having some kind of problem)